AOL File Library: 4,701 to 4,800

home *** CD-ROM | disk | FTP | other *** search

/ AOL File Library: 4,701 to 4,800 / aol-file-protocol-4400-4701-to-4800.zip / AOLDLs / Conference Logs and Sessions / LOG_ Staff Meeting 9_22_93 / CSS_0922.log next >

Wrap

Text File | 2014-12-11 | 48KB | 961 lines

***************************************** * Boot Camp for File Checkers * * For * * Company Support Staff * * * * September 22, 1993 * * * * Hosted by PC Tom * ***************************************** CSS Dennis: I would like you all to meet PC Tom. Tom is the FL for the PC Software Center and is CSS Dennis: also the Computing and Software guru. His training programs have been adopted CSS Dennis: throughout the PC side of AOL and his guidelines have become their standard. Tom has CSS Dennis: written several of the documents found in the CSS private area and he really helped me out o CSS Dennis: on the two that I authored. Please welcome Tom, no pie throwing or whatever. Also, to CSS Dennis: keep this rolling a modified protocol shall be in effect once we get really rolling. CSS Dennis: Tom? PC Tom: Thanks for the intro, Dennis! :) PC Tom: First think I'd like to say is that Bootcamp works best when Interactive. CSS Dennis: (I hope I spelled your name right) ;) PC Tom: So feel free to ask questions when necessary! :) PC Tom: I guess you did, Dennis! I didn't notice. :) CSS Dennis: :) PC Tom: First off Can each of you please tell me which computer you support, PC, MAC or Apple! CSS Miz: PC Windrose: Mac CSS Tracy: <=== PC ... CSS Mike: <--- PC and Mac CSS Alice: PC CSS Juno: PC CSS Bruce: Apple CSS Suzy: <-----PC and Mac CSS Robert: <------supports MAC CSS Dennis: <-- PC and A2GS CSS Gary: <--- PC CSS Wayne: <---PC PC Tom: Is that everybody? CSS Tony: Mac PC Tom: Just to let you know where I'm coming from.... CSS Dennis: yep PC Tom: I used to be the Applications Forum Leader on PC-Link. I always pushed for PC Tom: a more professional look to file descriptions and also making sure PC Tom: that sufficient information was given for a member to decide whether PC Tom: he wants to download a program. PC Tom: There is certain basic information needed.... PC Tom: Program name, type, author, and more important than anything, VERSION PC Tom: The guidelines I give for file descriptions have worked out well in PC Tom: Computing and Software PC Tom: From what I understand from Dennis, those supporting PC areas must follow PC Tom: the guidelines and those in other areas have a little more leeway. PC Tom: So, basically, what I'm going to cover is why we do things the way we do PC Tom: The main reason is that it PROMOTES DOWNLOADING by giving the PC Tom: essential information needed for someone to invest his time in downloading. PC Tom: It has to be perfectly clear to him that he is not downloading something PC Tom: that he already has. PC Tom: Anyway, just before DOS AOL and Promenade were launched, PC Tom: I was asked to write up guidelines and procedures for file checking. PC Tom: I can't take 100% credit for what is written, but I do believe it is all PC Tom: essential information. PC Tom: Before we talk about guidelines for file descriptions, lets first CSS Dennis: ! PC Tom: talk about Virus Checking PC Tom: GA Dennis CSS Dennis: I hope that all of you have had a chance to look over the documents in the library. They CSS Dennis: will help fill in the blanks and hopefully, give you some more questions to ask. :) CSS Dennis: GA PC Tom: RE: Virus Checking, I'm going to assume that you all know HOW to PC Tom: virus check. PC Tom: What I will talk about is the procedures that must be taken PC Tom: regarding the online requirements. PC Tom: That is..... What to do when someone reports a virus on a file he has downloaded,... PC Tom: and in the case of PC software, the required Virus detection software. PC Tom: I'll let Dennis tell you later what may be required for MAC. And I understand PC Tom: that there is no such problem with Apple software, is that right Dennis? PC Tom: First of all, why do we virus check?..... CSS Dennis: Not to date there hasn't been., (sorry, was locked up!) PC Tom: It provides a measure of protection and assurance to our online members and they expect us to PC Tom: We advertise that this is done. PC Tom: Every executable file must be checked for known computer viruses. PC Tom: Note the word, KNOWN. PC Tom: We can really only check for Known viruses and that's why we have procedures PC Tom: when viruses are reported. PC Tom: There can always be that window of opportunity where a virus PC Tom: gets by our checking. PC Tom: Hi Bob! CSC Bob: (hello... :) Don't let me interrupt... :) PC Tom: Fortunately in Computing and Software, we have never released a program PC Tom: that was later found to have a virus in it. CSS Dennis: Tom, as of today the standard for PC is v108 of McAfee's Scan?? PC Tom: We hope to keep that record. PC Tom: Yes, I'll get to that in a bit, Dennis! :) PC Tom: Actually, that was next on my list! :) PC Tom: For uniformity on the PC Side, we require SCAN by John McAfee to check for viruses. CSS Dennis: (was just a lead in :) PC Tom: And, we require that the latest version ALWAYS be downloaded from Online. PC Tom: John McAfee has a support area on AOL. Keyword = McAfee PC Tom: And, we have set up a convention where by searching on the words, VIRUS MCAFEE, using PC Tom: the file search utility, you can ALWAYS find the latest version. PC Tom: We keep that convention to make it easier for people to find what they like, PC Tom: and that sort of consistency occurs in all of the search words we have for other files and programs. PC Tom: One reason we require Scan to be downloaded from online is that we ALWAYS know PC Tom: it is from the author. PC Tom: His programs have been hacked in the past too. PC Tom: Another reason we use Scan is because it is probably one of the quickest to update, PC Tom: and usually gives less false reports than other programs. PC Tom: Before McAfee was online, we always went to his BBS and downloaded the file for here. PC Tom: So, we have always had a SAFE SOURCE. PC Tom: Now, that is not to say that you can ONLY use Scan to check programs. PC Tom: By the way, MAC people can interpolate this discussion to programs they use. :) CSS Dennis: (Disinfectant) CSS Dennis: L) PC Tom: We feel that everybody checking programs should use whatever they have PC Tom: at their disposal IN ADDITION to Scan. PC Tom: But, Scan gives us a tracking tool and knowing a history of past versions, PC Tom: we can pretty much know what the status is of programs online. PC Tom: Hi Jerry! CSS Jerry: hey! PC Tom: One thing I heartily recommend for everyone checking files is to also have a TSR monitor to PC Tom: check for unusual activity with your files. PC Tom: Remember though, that you can only use one Virus detection program at once. Windrose: TSR Monitor? PC Tom: SCAN, for example will find the signatures occasionally in some TSRs. PC Tom: TSR = Terminate and Stay Resident PC Tom: You run the program and it monitors activity such as if an executable file is being PC Tom: written to PC Tom: So, when you use Scan you have to be sure and boot from a protected floppy with the latest version of PC Tom: Scan on it. PC Tom: I'm sorry I can't translate this discussion to what you would do on a MAC. CSS Juno: ? CSC Bob: We will be covering that in another session, Tom. CSC Bob: Not a problem :) PC Tom: GA Juno CSS Juno: Tom, does this mean I can't boot from my hard drive when using Scan?? PC Tom: One reason not to boot from your hard drive when using SCAN is so you PC Tom: avoid any viruses that may be active on your computer already. Usually PC Tom: not a problem, and it checks for them. PC Tom: Scan will check the programs you ask it to, or even check your entire PC Tom: hard drive PC Tom: After you have done that check, you can boot from your hard drive and then CSS Juno: OK, hoping my 5 1/4" floppy drive still works ;) PC Tom: test the program for functionality. PC Tom: When you test your program for functionality, here's where it is nice PC Tom: to have a TSR Monitor. PC Tom: I usually use VDEFEND that came with Central Point's PC Tools. PC Tom: I set it to alert me when an executable file is being written to. PC Tom: Sometimes a problem when downloading a .EXE file from online, as it PC Tom: tells me that program is being written to. :) CSS Dennis: ? PC Tom: GA Dennis CSS Dennis: Tom, I know this may be a sore subject with some but what are your feeling of the check file CSS Dennis: program that comes with DOS 6.0? I've heard it was a good rudimentary checker to see if CSS Dennis: files have been written to. CSS Tracy: ! PC Tom: Actually, I'm using it now as my TSR. PC Tom: GA Tracy CSS Tracy: Dennis, CSS Tracy: MSAV is a nice program, but it is a subset of VSAFE and CPAV CSS Tracy: which come from Central Point. As such, it cannot necessarily CSS Tracy: see all the viruses that CPAV can, especially if you are dealing with CPAV 2.0. CSS Tracy: <---done CSS Dennis: (thanks Tracy!) PC Tom: I haven't explored CPAV 2.0 and you may be right. PC Tom: One thing to note. Keyword = NORTON gets you to Symantecs Norton Anti-Virus support PC Tom: They also support MAC virus signatures, Windows signatures, etc. PC Tom: Keyword = CENTRAL gets you to Central Point Software's support area online PC Tom: and they also have support for MSAV there. PC Tom: As well as their other virus checking/detection programs. PC Tom: Do they have MAC support there Dennis? CSS Dennis: Not sure, Any Mac types know? PC Tom: Anyway, we are fortunate to have all three, McAfee, Central, and Norton, online CSS Tracy: Yes, they do.... CSS Dennis: What is this, Mac types forget how to type? Windrose: Yes :) PC Tom: Thanks, Tracy and Windrose! :) Windrose: We only know how to point and click ;P PC Tom: All three are good programs and rate highly in any test lab for virus checking. CSS Robert: <---this MAC type was checking keywords NORTON & CENTRAL and didn't find anything. :/ PC Tom: And, I can't emphasize the importance of having a TSR monitor when PC Tom: testing for functionality. PC Tom: That can also alert you to Trojan programs, which we do not necessarily PC Tom: test for because we can't run a program that much. CSS Mike: Keyword SYMANTEC will get ya there PC Tom: You are most vulnerable to those types of things, so be sure to have something PC Tom: to protect yourself, and actually, nothing is better than a good BACKUP of your PC Tom: hard disk. PC Tom: Try CENTRAL POINT, Robert. Those are the official keywords. ;) PC Tom: Now, what to do if someone reports to you that they found a virus PC Tom: Similar procedures should apply to all of you. PC Tom: First of all, when a virus is reported, you MUST take the member seriously PC Tom: You must hide the file and check it again. PC Tom: Remember, we can only check for KNOWN viruses, and something may PC Tom: have slipped through the cracks. PC Tom: You should notify your Tier 1 person. Is that the right terminology, Dennis? CSS Dennis: Yep! Right out of the manual :) PC Tom: And for PC file, I would appreciate your Tier 1 person notifying me. CSC Bob: (And if I can insert... I ALSO want to know immediately of any reported virus, PC Tom: I keep track of those things and also want to know how its been handled. CSC Bob: and what the results of the check are) CSS Dennis: (someone wake Mike up and tell him about this :) PC Tom: Mainly, so I can modify my bootcamps to cover something that may have slipped through. CSS Mike: <--- awake :) CSC Bob: ::nudging mike:: PC Tom: Right! I want to know the results, too! :) PC Tom: There are exceptions to hiding the file. If its one that you KNOW always gives PC Tom: a false report for a particular virus, then PC Tom: simply check it again with the latest virus checking software. PC Tom: Also, you want to jump on that task with two feet and get back to the PC Tom: member with the results. CSS Bruce: got bumped offline :( PC Tom: You do want to get someone else involved in checking it too in many cases. PC Tom: If the person used XYZ virus checker, try to find someone you know who PC Tom: also has that virus checker. PC Tom: There are some virus checkers, by the way that aren't worth Squat PC Tom: on the PC Side. Usually commercial programs by a small company or author. PC Tom: Always good to double check things as best you can. PC Tom: And, if the person has posted a message on a message board, leave his message there CSS Dennis: As with all the stuff involving CSS, when in doubt, ask! PC Tom: but post an answer right away that you are checking it and get back CSS Tony: Question PC Tom: to the message board with a posted response. PC Tom: GA Tony CSS Tony: How does Virex Rate? PC Tom: I don't know! :) CSS Robert: ! PC Tom: Ask PC Glenn! :) PC Tom: GA Robert PC Tom: PC Glenn is the Telecom Forum Leader and handles the Virus program information CSS Robert: I think Virex is great with the MAC, and I know that Dennis has praised it as well, right Den? CSS Tony: ! CSS Dennis: Most definitely :) CSS Tony: CSS Deb also recommended it to me, PC Tom: GA Tony. Were you talking about a PC program? CSS Tony: The Mac version PC Tom: Well, just remember that SCAN is required first. :) CSC Bob: The Mac version is very good. PC Tom: for PCs PC Tom: I can't talk to any of the MAC checkers and probably Glenn can't either. PC Tom: One reason for getting your answer posted or in e-mail to the member is so PC Tom: they don't go reporting all over the place that they found a virus on AOL. PC Tom: We had one guy do that on CompuServe once. Fortunately Glenn came across PC Tom: his post and printed a retraction because it was a false report. PC Tom: We probably got a dozen false reports on that program, even with Scan. PC Tom: So answer quickly. :) PC Tom: Any questions about virus checking? CSS Tracy: ? PC Tom: Oh! Also, if a person reports on a message board, also send him e-mail. :) PC Tom: GA Tracy CSS Tracy: If a file shows a known "false positive" to a specific virus checker, can we put that CSS Tracy: in the file description? PC Tom: If it becomes a big enough problem. No harm in that! :) PC Tom: One thing we never do on the PC Side is tell which program we use for checking PC Tom: for viruses. PC Tom: We feel that it is not necessary that they know that, and also it keeps us PC Tom: out of trouble if a "Know it all" thinks things should be done differently. PC Tom: He could discredit us unfairly on another online service and we'd never know about it. CSC Bob: (There is a bit different policy on the Mac side, and we will cover it then) CSC Bob: (That's the beauty of this system... different ways for different folks...:) PC Tom: Right, Bob! Was just going to say that. :) PC Tom: Do you want to cover that now, or in your other training sessions? CSC Bob: We will cover that later, Tom... PC Tom: OK! If no more questions on virus checking, lets go to file descriptions. CSC Bob: But suffice it to say that they do post the virus checker in the file description. CSC Bob: No biggie PC Tom: First of all, again the MAC and Apple side doesn't have to follow the format we PC Tom: do for PC files. But, since the PC Files are going to be in our file search utility PC Tom: eventually, they should be followed for PC Files. CSS Dennis: The big one! PC types, please pay close attention. File naming conventions are very CSS Dennis: important. PC Tom: One thing I'd like to say to start off by saying is that there are very good PC Tom: reasons for our conventions PC Tom: First of all, we make sure that certain information is conveyed. PC Tom: The subject line always starts off with a word that is in all caps that I call PC Tom: a Generic Label. PC Tom: The guidelines you have say FILENAME, but please substitute label for that. PC Tom: The Generic Label is very much like a filename, but void of those things PC Tom: that make a filename unique to that version. PC Tom: Think of the label more like a name that you would use to call the program. PC Tom: It is something that we like to be consistent over all versions of that program PC Tom: So, if a person uses that all caps label to search for a file, he should PC Tom: always be able to find the latest version. PC Tom: The conventions we have regarding consistency between file descriptions PC Tom: for future versions also helps the Forums maintain their libraries. PC Tom: When they search to see what the current version is online, they should be able PC Tom: to find ALL versions that may be online. PC Tom: We instruct them to use the all Forum search as it is just as important PC Tom: to notify another Forum when your Forum has a newer version. PC Tom: Some programs overlap Forums and will be in both on the PC Side. PC Tom: Before I go on about the Generic Label, there are exceptions where it won't be a generic CSS Dennis: ! PC Tom: program name. PC Tom: GA Dennis CSS Dennis: y'all, this is especially important when your company bridges platforms. Make sure that the CSS Dennis: PC file is named correctly per Tom's instruction. The Mac file, perhaps of the same program CSS Dennis: will follow the Mac guidelines. (We will cover that one later) CSS Dennis: thanks Tom. PC Tom: Thanks, Dennis! PC Tom: The exceptions to the Generic Label naming conventions occur mostly in PC Tom: the Graphics Forum, Music and Sound, and DeskMate PC Tom: It those Forums, it is more important to tell the type of file. PC Tom: That is, GIF, PCX, MOD, ADLIB, DMUSIC, etc. PC Tom: That way, a person with a Sound Blaster will always know which files support the Sound Blaster. PC Tom: Can't remember the name they use. Think it is CSS! :) PC Tom: Any way, lets do an anatomy of the file description. PC Tom: The searchable fields in a file description are as follows. If different for MAC and Apple, Dennis, PC Tom: please chime in. :) PC Tom: SUBJECT: PC Tom: FILENAME: PC Tom: UPLOADER: PC Tom: Keywords: PC Tom: Notice we don't have Author as a searchable field. PC Tom: Well, we take care of that by putting either the Author's last name, or company name, or both PC Tom: in the Keywords line. PC Tom: Sometimes it is very helpful in finding a file if you know the author. PC Tom: When I discuss the Keywords line, I prefer to discuss "Search Words" PC Tom: This eliminates a problem when describing to a member how to find a file PC Tom: since we do have a real function online called Keywords CSS Dennis: ! PC Tom: Keywords: is a library term, and looking back, it might have been better to PC Tom: have called that line something different. PC Tom: GA Dennis CSS Dennis: Let take a second to clarify something that came up this week. We use keywords two CSS Dennis: different ways online. There is an AREA keyword i.e.; Passport to take you to the CSS Dennis: Passport company area, and then there are FILE keywords, as Tom will now CSS Dennis: describe that aid in locating files via the QuickFinder or other search engine. CSS Dennis: GA PC Tom: Actually, the rest of the time tonight is basically a lesson in finding files online. PC Tom: If you KNOW HOW TO SEARCH, you will know how to enter the right words PC Tom: to find a file using the search. PC Tom: I like to say that if I can't find a file using the search within a couple minutes, PC Tom: that you don't have the right search words. :) PC Tom: Let's ask a question of you now.... Should we recommend to a member that he search on a specific PC Tom: filename? PC Tom: Anybody care to answer? CSS Mike: I do it. CSS Mike: Example: Dazzle PC Tom: GA Mike CSS Miz: Nope, cause filenames can change with version numbers. CSS Mike: Rats. I don't win the pizza? PC Tom: Well, Mike, that isn't always the filename. That's the Generic Label, and PC Tom: perfectly acceptable. :) PC Tom: Miz is right! Filenames change. PC Tom: Even though it might get them that particular file, it is better to recommend CSS Mike: :::promoting Miz to Tier 1 1/2::: CSS Miz: <-- did her homework. :) CSS Juno: Way to go Miz!! PC Tom: something more generic that will ALWAYS find the latest version for the member. PC Tom: Get them OUT of the habit of searching on filename. PC Tom: This promotes downloading too. If they can't find the latest version of their PC Tom: favorite program, they can't download it. PC Tom: Probably 80 percent of the time, the generic label will find just what the person needs, PC Tom: and always find it regardless of whether the file was updated. PC Tom: That's not including GIF, MOD, ADLIB, etc. as you can surely see. :) PC Tom: One thing also important is that even some Generic Labels are just a bit too PC Tom: generic. PC Tom: Take the program, LIST, by Vernon D. Buerg. PC Tom: If you search on LIST, you'll get more matches than you care to wade through. PC Tom: But, by adding the author's last name, which is one of the search words in the PC Tom: keywords: line, you can find it easily. Tell them to search on LIST BUERG PC Tom: I always give my search words as all caps. Easier for them to see just PC Tom: what they are. :) PC Tom: To the member, when telling him to search, that is. ;) PC Tom: In the file descriptions, we use capitalized words with the rest small, CSS Dennis: :) PC Tom: as appropriate. Also, we have a comma between words. MAC descriptions don't have the commas CSS Robert: (((justoneheckofalongwordsometimes))) PC Tom: I was at a Harvard Graphics seminar yesterday, and they enforced something PC Tom: that I believe fully. PC Tom: We were told that when a LINE IS ALL CAPS, IT CAN'T BE READ as easily as when only PC Tom: capitalizations are used as appropriate. CSS Tracy: Hear! Hear!!! PC Tom: With our Subject line for PC Files, only the Generic Label is all caps. PC Tom: To me, it seems to pull a focus to the list of subjects. CSC Bob: Sorry, Tracy... that should have been HEAR HEAR!!! CSS Tracy: :) PC Tom: I don't know why, but it is easier for me to read a list of subject lines PC Tom: than when that first word is small letters. PC Tom: Also, we put the Version number in our subject line. PC Tom: Why? Because this is the first thing that a member sees. PC Tom: He doesn't have to open a file description to see if it is a new version or old. PC Tom: We get the jump on him by telling him right off as much as we can about the program. PC Tom: So, he doesn't pass it by. PC Tom: We avoid abbreviations or acronyms in our subject line. PC Tom: But, if you must abbreviate, then be sure to put the full word (if it is an important word) PC Tom: in the Keywords: line. PC Tom: Before I get off all caps, one more thing. PC Tom: If you notice in the PC File descriptions, we don't use all caps for PC Tom: Keywords: or Type: PC Tom: This is for the same reason as discussed above. It breaks up the file PC Tom: description to make it read easier. PC Tom: We also leave an extra line after NEEDS: CSS Dennis: ! PC Tom: You want to make sure that your search words are unique enough to get good results! PC Tom: For example, ZIP isn't a good search word for PC Files unless you want to see PC Tom: 30,000 or more matches. :) PC Tom: GA Dennis CSS Dennis: I think it should be noted that there MUST be a blank line before the Keywords: line. This CSS Dennis: is a requirement of the Stratus. If no blank line, chances are that the Keywords: line will CSS Dennis: not be picked up by the search compilation. PC Tom: I didn't know that, Dennis! :) CSS Dennis: Yep! ;) CSC Bob: A note... PC Tom: Another thing about the keywords: line and also the subject line.... PC Tom: GA Bob CSC Bob: I know that at first it is going to be difficult remembering which rules to follow... CSS Dennis: C# ?? :) CSC Bob: but it really will be important... CSC Bob: Not that one is better than an other... CSC Bob: ( See... I'm impartial... LOL!!! And a politician.. I'm covering all bases... :) CSC Bob: But it is important for the sake of the member to see consistency... CSC Bob: so... no matter which you prefer... they are both right... :) CSC Bob: Isn't THAT a grand thing?? :) CSC Bob: end of note..:) PC Tom: Right, Bob! Consistency is the best rule. :) You want to develop a familiarity PC Tom: with the product for the members. CSS Tracy: ? PC Tom: GA Tracy CSS Tracy: What about vendors with cross-platform files in the same library? PC Tom: I'm sort of hoping that things will be arranged so that libraries are separate for each Platform. Any PC Tom: word on that, Bob? CSC Bob: nope... CSC Bob: not necessarily, Tom.. CSC Bob: It will be nice if we ever get to that point... PC Tom: Would be much better, but I guess we can't fight city hall! :) CSC Bob: But we do have resources to keep in mind. CSS Tracy: So in the meantime...? CSC Bob: We'd prefer separate message boards before libraries... :) PC Tom: If files are in the same library, you had better make sure that it is obvious to the CSC Bob: In the mean time, follow the conventions for each side with the different files PC Tom: downloader, who may be a new member, that it is for the MAC or PC, etc. CSC Bob: We have also been including MAC or PC in the subject line as possible.. CSC Bob: And... there is this line in the file description that calls for a list of equipment needed. CSS Jerry: ! PC Tom: That's a good point when libraries are intermixed. CSC Bob: That's a good place to list it as well. PC Tom: Subject line, that is. :) CSC Bob: One problem is that many folks don't bother to read file descriptions...sigh PC Tom: The whole idea is to minimize work for yourselves with what you have CSC Bob: ga PC Tom: in the subject line, as well as sell the program to the member. PC Tom: If you can tell at a glance without opening a file description, your job PC Tom: of maintenance will be much easier. Or should I say, MUCH EASIER! :) PC Tom: Before I forget, there are a couple of thing I'd like to say about the length of a subject line PC Tom: and the number of search words on the Keywords: line. PC Tom: First of all, sometimes your subject line will extend past 32 characters on the PC Side. PC Tom: Not sure about the MAC side. PC Tom: When this happens, only the first 32 characters can be used to search. PC Tom: I ran into that problem today. A word overlapped the 32 characters PC Tom: and I couldn't find the file until I deleted that last search word. PC Tom: Deleted from my search, that is. PC Tom: So, if you have to put more in the subject line than 32 characters, only the PC Tom: first 32 will count in the search, and that partial word hanging in there PC Tom: can't be searched. PC Tom: You could probably search on those few characters, though, but that's not good. :) PC Tom: There is a physical limit to the length of the Keywords: line. CSC Bob: <---- doesn't know any 32 character words... hehe PC Tom: LOL! What I mean is that word at the end that goes from say, character 29 to 38. CSS Tony: SUPERCALIFRAGILISTICEXSPIALIDOCIOUS? CSS Jerry: <---was thinking that...sadly enough PC Tom: Just put those words important to your search earlier in the subject line. :) PC Tom: 60 characters for search words is a good number to shoot for. PC Tom: Not including the words, Keywords: <Space><Space><Space> CSS Tony: ? PC Tom: You can actually go longer, but if you go two full lines more, some at the end won't be searched. PC Tom: GA Tony CSS Tony: <word> is that what is is or is that a physical space? PC Tom: physical space PC Tom: Start counting from your first search word including commas. PC Tom: If you have to, the commas can be eliminated for PC Files, but I personally PC Tom: think it looks better. PC Tom: Start each word with a capital letter. Sometimes two words can make up one search word. PC Tom: Try to make sure that the words you select don't cause too many matches when searching. PC Tom: Try to be unique enough to find your file and perhaps a class of files. PC Tom: Remember when I said that ZIP wasn't a good word to use? PC Tom: Well even so, we sometimes put that in the keywords line for emphasis PC Tom: on what the program uses, such as a shell for PKZIP. CSS Wayne: ? PC Tom: which is our primary ZIPing and unZIPing program. PC Tom: GA Wayne CSS Wayne: Could we take an example? PC Tom: Well, probably "Database" would get too many matches while searching. CSS Wayne: For example, let's say that Cardinal Technologies has uploaded a windows driver PC Tom: But, you may want to put that pm the keywords line. CSS Wayne: for one of it's video cards (VGA500) CSS Wayne: What would you suggest for keywords? PC Tom: Keywords: Cardinal, Video, VGA, driver, Win31 PC Tom: Actually, if you have any of those words in your subject line, don't put them in the keywords: line CSS Mike: VGA turns up a lot of matches too, though. Takes you to GIF files and everything else. PC Tom: VGA in certain instances can be a good word to use. CSS Dennis: ? PC Tom: More for information, and when used with other search words. CSS Wayne: ? PC Tom: For example, let's say you are looking for a Windows driver. PC Tom: Win31 is on most of the Windows programs. PC Tom: Or Win3x PC Tom: You can use CARDINAL VGA WIN31 to find it PC Tom: Your other words eliminate the Graphics files, Games files, etc. PC Tom: VGA eliminates the CGA, EGA, and SVGA drivers. CSC Bob: Tom... is there a list of common search words anywhere? Reason I ask is i wouldn't have CSC Bob: thought to look for WIN31... WIN, perhaps... but not the other... CSS Dennis: (cancel my ?) CSC Bob: If there is a common list, this might help PC Tom: Well, actually, there are common search words on the PC Side at least. PC Tom: I don't have a list, but each library can be set up with common search words. PC Tom: Win31 is probably redundant, but its an easy thing to look for when looking PC Tom: at a file description to see just what the program is for regarding Windows version. PC Tom: When I was FL in Applications, I set up a bunch of common search words for each library. CSC Bob: Wouldn't Win 31 work better, as then WIN would pull it up? PC Tom: That information might be all lost now. PC Tom: It used to be that numbers couldn't be searched on separately. PC Tom: I think that has been corrected, but you sort of get locked in. :) PC Tom: WINDOWS will bring up all the Windows programs. CSS Wayne: <---still holding up hand.... :) PC Tom: Sorry, Wayne! Thought you canceled that. :) GA PC Tom: Guess that was Dennis! :) CSS Wayne: Should plurals be used? ie DRIVERS vs DRIVER PC Tom: If you search on DRIVER, it will also find DRIVERS, and vice-versa PC Tom: But, that reminds me. Use the "ing" form for things like "Word Processing" PC Tom: rather than Word Processor PC Tom: The problem you come into with plurals is when a plural has an ES CSS Dennis: well Hi Don! :) CSS Donald: Can you say Late...? I knew you could...Sorry CSS Donald: Got called away to work late this afternoon. :( PC Tom: That's ok, Don! You can come to the next one. :) PC Tom: Welcome to stay now, too! :) CSS Donald: :) Figured.:) Detention. PC Tom: One thing you may have noticed when I've been talking about the File Descriptions is that CSS Wayne: (He got here just in time for the closed book test!) :) PC Tom: I basically talk about the header information only. Footer information will also be covered. PC Tom: The main body of the text is pretty much what you or the company you support PC Tom: wants to say. PC Tom: Don't re-invent the wheel if you don't have to. PC Tom: The Author usually knows what he wants to say to promote his program. PC Tom: Its perfectly ok to lift his words. PC Tom: Then he can't complain about your file description! :) PC Tom: I would advise you to try to eliminate the "Better than sliced bread" type of statement, though. PC Tom: Try to keep the main body of the file description objective. PC Tom: Is that the right word? PC Tom: Anyway, don't make claims that can't be supported. CSS Dennis: ! CSC Bob: Comment....As this stuff is all from companies... CSC Bob: We want to make sure that they put in their description WHAT the BENEFIT of the file is CSS Dennis: (hehehehe, Bob snagged before I could) CSC Bob: I get HUGE mail asking me what a file does... CSC Bob: Why do I need it... CSC Bob: What is the benie of this over the previous... CSC Bob: That need isn't so great when it is a demo file... PC Tom: That's fine to put the benefit. Just make sure you don't say "Better than any other program" CSC Bob: That's not the point, Tom. CSC Bob: We have a bit different situation with companies... PC Tom: OK! Was going to cover that next. :) CSC Bob: In that these are their official files... CSC Bob: and they not only can but SHOULD say what the file does... CSC Bob: If it's a member upload in a company library, that is a different situation. PC Tom: Basically, you don't want them to lose credibility, and probably that won't be a problem. CSS Robert: ? PC Tom: You also want to add in what's new with this version. PC Tom: GA Robert CSS Robert: There seems to be a fine line here...how do you keep from giving the impression that AOL supports CSS Robert: a statement from the company that his product is the BEST? CSC Bob: I can take this one... PC Tom: That's basically what I was driving at. I guess Bob would be in a better position to handle this. :) CSC Bob: The files are uploaded by the company.... CSC Bob: It isn't our responsibility to tell them what to say in their file description. CSC Bob: If it looks really outrageous, then it will make them look that way. CSS Robert: It's their billboard...free and clear??? CSC Bob: This isn't quite the same situation that you run into in the forums... CSC Bob: No... I don't think I'd say that... PC Tom: Most likely they will be smart enough to give you the right text. :) CSC Bob: What you might want to do is to point out what is really silly to Mike, or Pam, or Dennis... CSC Bob: And they might jump in... CSC Bob: You guys are not censors ... CSC Bob: You are there to help them with their files... PC Tom: That is probably the best way. I'm not trying to edict that. :) CSC Bob: You can make suggestions. CSS Mike: Yeah, my staff should think of themselves as future editors. :) CSC Bob: You can do all kinds of things... CSC Bob: but they may have to put certain things in for their own benefit. CSC Bob: or the benefit of their company. PC Tom: Good points, Bob! CSC Bob: It is important to remember that we have a bit different position CSC Bob: than the forums. The forum staff are fully in charge of their forum... PC Tom: Well, lets wrap up with a few more thoughts. CSC Bob: And they can do anything they want... CSC Bob: We are not... CSC Bob: We work for the company... CSC Bob: (as long as they stay within TOS) CSC Bob: does that help? CSS Robert: you bet...thanks PC Tom: First of all, you need to make sure that essential information is there. PC Tom: Your best bet is to try and use the same header info in the file description for updates, PC Tom: Same keywords line, too, unless something is added that is also important. PC Tom: You really want to provide enough information to SELL the program and make it easy PC Tom: to search for. PC Tom: You don't want to write a treatise on how to install it, but if there PC Tom: seems to be a lot of questions on that, perhaps advise the company that they PC Tom: might want to cover that in the next description, through your Tier 1 people, I guess. CSC Bob: (whichever is most comfortable) PC Tom: At the bottom of a file description, for PC Files, we put a CSS Dennis: Good idea Tom. Again, if there are problems, notify your T1 so they know what's going on. PC Tom: To run, enter: [FILENAME (Options)] PC Tom: Then: PC Tom: Documentation: [FILENAME.DOC] PC Tom: Downloads for previous version is next. Not one of my favorites, but part of the guidelines. :) CSS Tracy: ? PC Tom: In closing, one thing I'd like to say is that you can feel free to ask me a question at any time. PC Tom: via e-mail, etc. PC Tom: IM's PC Tom: GA Tracy CSS Tracy: Is Downloads for Previous Versions cumulative? PC Tom: I think that's the way most people put it. Versions: CSS Tracy: Cool.... PC Tom: I think its hard to track! :) PC Tom: But, in your areas, it might not be. CSS Dennis: Tom, better to leave off completely if don't know? This is optional isn't it? CSS Wayne: (Not all files are executables or text.....) PC Tom: I would say, optional. So, when your area gets started, it probably wouldn't be there. PC Tom: "Downloads" doesn't imply executable. Could be informational text. :) PC Tom: I have an article on Virus Checking that I'll be sending to Dennis to PC Tom: post for you all. PC Tom: Its called Virus Checking and Why? PC Tom: And covers many of the things we talked about for Virus Checking. PC Tom: Any questions before we close? CSS Wayne: I was referring to the TO RUN.... part.... CSS Robert: Here's to those who made it to the end............. CSS Tony: Are we there yet? CSS Tony: :) PC Tom: Well, of course you wouldn't have that line for a text file. :) CSS Miz: LOL, Tom :) CSS Dennis: I want to thank Tom for being able to spend the time with us tonight. I'm sure you PC types PC Tom: If no questions, then thanks for coming! You've all been great with your questions.:) CSS Dennis: will be able to better understand the whys and wherefores in your area now. As Tom said, if CSS Wayne: Thanks Tom! CSS Juno: thank you Tom, and are you sure you are ready for all the help IMs?? ;D CSS Miz: Thanks, Tom!!! :D CSS Robert: <---offering a toast...Y.Y Y Y Y Y Y Y Y Y Y Y Y Y Windrose: Thanks, Tom!! Good night everyone :) CSS Dennis: you have any questions at all, please feel free to contact him or me. CSS Tracy: ::: clapping vigorously::: CSC Bob: Way to go, folks... :) PC Tom: I really enjoy working with people, Juno! So, yes, I'm ready! :) CSS Dennis: For the Mac and A2's, we'll be covering the specifics of your files in an abbreviated lesson CSS Wayne: ::::Setting up keyboard macro.....IM PC Tom::: :D CSS Bruce: bounced again CSS Juno: LOL Wayne, EM it to me, I know I will need it ;D CSS Dennis: to be scheduled later. Also, coming up: Rainman and message board tools! CSS Tracy: <groan> CSS Miz: :::: passing punt pillow to Bruce ::::: CSS Robert: <----MAC USER: HUH? CSS Wayne: :) CSS Bruce: <----- fades back and CATCHES it!!!!!! CSC Bob: We gonna train you folks to the teeth...:) CSS Dennis: Specifics like the Mac requirements Robert. ) CSC Bob: How do you feel about Amtrak??? :) CSS Robert: uh oh! :/ CSS Juno: Wait, Bob, was this what we bargained for, all training and no action ;D CSS Miz: Oh, nice catch, Bruce! PC Tom: I'll pass on a log to Dennis tomorrow.